Skip to content

[Snyk] Fix for 1 vulnerabilities#12239

Closed
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-152273b8ef84d6bb0f33219e351dbc2b
Closed

[Snyk] Fix for 1 vulnerabilities#12239
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-152273b8ef84d6bb0f33219e351dbc2b

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io Bot commented Feb 13, 2026

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • plugins/catalog-backend-module-ldap/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-AJV-15274295
  685  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)


EntelligenceAI PR Summary

Pins Backstage dependencies to explicit versions in the LDAP catalog backend module package configuration.

  • Replaced workspace:^ protocol with version 0.6.1 for @backstage/backend-tasks
  • Replaced workspace:^ protocol with version 0.1.1 for @backstage/catalog-model
  • Replaced workspace:^ protocol with version 0.1.0 for @backstage/plugin-catalog-common
  • Replaced workspace:^ protocol with version 1.0.0 for @backstage/plugin-catalog-node
  • Transitions from monorepo workspace dependency management to explicit version locking

@codesandbox
Copy link
Copy Markdown

codesandbox Bot commented Feb 13, 2026

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@snyk-io
Copy link
Copy Markdown
Author

snyk-io Bot commented Feb 13, 2026

Snyk checks have failed. 1 issues have been found so far.

Status Scanner Critical High Medium Low Total (1)
Open Source Security 0 0 1 0 1 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@socket-security
Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
License policy violation: npm argparse under Python-2.0.1

License: Python-2.0.1 - the applicable license policy does not allow this license (4) (package/LICENSE)

From: ?npm/js-yaml@4.1.0npm/argparse@2.0.1

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/argparse@2.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
License policy violation: npm caniuse-lite under CC-BY-4.0

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (npm metadata)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/package.json)

License: CC-BY-4.0 - the applicable license policy does not allow this license (4) (package/LICENSE)

From: ?npm/@docusaurus/core@0.0.0-5591npm/@docusaurus/plugin-client-redirects@0.0.0-5591npm/@docusaurus/preset-classic@0.0.0-5591npm/caniuse-lite@1.0.30001481

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001481. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm entities is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: ?npm/@docusaurus/core@0.0.0-5591npm/@docusaurus/plugin-client-redirects@0.0.0-5591npm/@docusaurus/preset-classic@0.0.0-5591npm/entities@4.4.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.4.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@entelligence-ai-pr-reviews
Copy link
Copy Markdown

Walkthrough

This PR transitions the LDAP catalog backend module from workspace protocol dependency references to explicit version pinning. Four Backstage packages are updated with specific version numbers: backend-tasks (0.6.1), catalog-model (0.1.1), plugin-catalog-common (0.1.0), and plugin-catalog-node (1.0.0). This change moves away from the monorepo workspace dependency management pattern (workspace:^) to locked versions, which is typically done in preparation for package publication or to ensure consistent dependency versions across environments.

Changes

File(s) Summary
plugins/catalog-backend-module-ldap/package.json Updated four Backstage package dependencies from workspace protocol references (workspace:^) to explicit versions: @backstage/backend-tasks to 0.6.1, @backstage/catalog-model to 0.1.1, @backstage/plugin-catalog-common to 0.1.0, and @backstage/plugin-catalog-node to 1.0.0.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant Backstage as Backstage Backend
    participant LDAP as LDAP Catalog Module
    participant Tasks as Backend Tasks
    participant CatalogNode as Catalog Node
    participant LDAPServer as LDAP Server
    participant CatalogModel as Catalog Model

    Note over LDAP: Module now uses pinned versions:<br/>backend-tasks: 0.6.1<br/>catalog-model: 0.1.1<br/>catalog-common: 0.1.0<br/>catalog-node: 1.0.0

    Backstage->>LDAP: Initialize LDAP provider
    LDAP->>Tasks: Schedule periodic sync task
    
    loop Periodic Sync
        Tasks->>LDAP: Trigger LDAP sync
        LDAP->>LDAPServer: Query users/groups
        LDAPServer-->>LDAP: Return LDAP entries
        LDAP->>CatalogModel: Transform to catalog entities
        CatalogModel-->>LDAP: Validated entities
        LDAP->>CatalogNode: Ingest entities
        CatalogNode-->>LDAP: Confirmation
    end
Loading

▶️AI Code Reviews for VS Code, Cursor, Windsurf
Install the extension

Note for Windsurf Please change the default marketplace provider to the following in the windsurf settings:

Marketplace Extension Gallery Service URL: https://marketplace.visualstudio.com/_apis/public/gallery

Marketplace Gallery Item URL: https://marketplace.visualstudio.com/items

Entelligence.ai can learn from your feedback. Simply add 👍 / 👎 emojis to teach it your preferences. More shortcuts below

Emoji Descriptions:

  • ⚠️ Potential Issue - May require further investigation.
  • 🔒 Security Vulnerability - Fix to ensure system safety.
  • 💻 Code Improvement - Suggestions to enhance code quality.
  • 🔨 Refactor Suggestion - Recommendations for restructuring code.
  • ℹ️ Others - General comments and information.

Interact with the Bot:

  • Send a message or request using the format:
    @entelligenceai + *your message*
Example: @entelligenceai Can you suggest improvements for this code?
  • Help the Bot learn by providing feedback on its responses.
    @entelligenceai + *feedback*
Example: @entelligenceai Do not comment on `save_auth` function !

Also you can trigger various commands with the bot by doing
@entelligenceai command

The current supported commands are

  1. config - shows the current config
  2. retrigger_review - retriggers the review

More commands to be added soon.

@github-actions
Copy link
Copy Markdown

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

@github-actions github-actions Bot added the stale label Feb 20, 2026
@github-actions github-actions Bot closed this Feb 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants